Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

Log Entry Types (-logentrytypes)

Use Log Entry Types (-logentrytypes) to specify one or more types of log entries to write to the log file specified by the Client Logging (-clientlog) startup parameter.

Operating system and syntax	UNIX Windows	-logentrytypes string
Use with	Maximum value	Minimum value	Single-user default	Multi-user default
Client Session	–	–	–	–

string

A character string that specifies a comma-separated list of log entry types.

By default, the logging level you specify using the Logging Level (-logginglevel) startup parameter applies to all log entry types specified. However, you can specify a different logging level for each entry type, as follows:

log-entry-type[:level]

log-entry-type

A log entry type listed in Table 4–2 below.

level

A logging level value (between 0 and 4).

Table 4–2 describes the log entry types.

Table 4–2: Log entry types

Log entry type	Executable	Description
4GLMessages	4GL (GUI and character mode). AppServer and WebSpeed do not require this log entry type for 4GL messages to be written to the log file.	The 4GL interpreter writes all 4GL VIEW-AS ALERT-BOX messages to the log file, together with the 4GL stack, when you turn on Debug Alert, using either the Debug Alert (-debugalert) startup parameter or the DEBUG-ALERT attribute on the SESSION system handle.
4GLTrace	4GL clients, AppServer, and WebSpeed agents.	Turns on logging for the execution of internal procedures, user-defined functions, persistent user-interface triggers, and named events (generated by the RUN, FUNCTION, PUBLISH, and SUBSCRIBE statements, respectively). It also logs the instantiation of classes (generated by the NEW statement) and the invocation of methods defined within classes (generated by the SUPER method and the DELETE OBJECT statements).
AiaMgmt AiaProp AiaRqst AiaUbroker AiaDefault	AIA.	Turns on logging for the AIA component.
ASDefault	AppServer agent.	Combines the ASPlumbing and DB.Connects log entry types. It is the default value for AppServer agents.
ASPlumbing	AppServer agent.	Turns on logging for different actions, depending on the logging level specified.
DB.Connects	4GL clients, AppServer, and WebSpeed agents.	Turns on logging of database connections and disconnections. The log messages include database name and user ID number.
DynObjects.DB DynObjects.XML DynObjects.Other DynObjects.Class DynObjects.UI	4GL clients, AppServer, and WebSpeed agents. 4GL clients and WebSpeed agents.	Turns on logging for creation and deletion of database objects, dynamic objects, user interface objects, and classes.
FileID	4GL clients, AppServer, and WebSpeed agents.	Turns on logging for file opening, file closing, and error messages that do not contain the filename.
MsgrTrace	WebSpeed Messengers.	Turns on logging for WebSpeed Messengers. The information logged depends on which Messenger is running and the logging level specified.
NSPlumbing	NameServer.	Turns on logging for the NameServer component.
ProEvents.UI.Char ProEvents.UI.Command ProEvents.Other	4GL clients, AppServer, and WebSpeed agents.	Turns on event logging for different categories of events.
QryInfo	4GL clients, AppServer, and WebSpeed agents.	Turns on logging for query resolution statistics.
SAX	4GL clients, AppServer, and WebSpeed agents.	Turns on logging for the SAX parser.
UBroker.Basic UBroker.ClientFSM UBroker.ServerFSM UBroker.ClientMsgStream UBroker.ServerMsgStream UBroker.ClientMsgQueue UBroker.ServerMsgQueue UBroker.ClientMemTrace UBroker.ServerMemTrace UBroker.ThreadPool UBroker.Stats UBroker.AutoTrim UBroker.All	Unified Broker.	Turns on logging for the Unified Broker component.
WSADefault	Web Services Adapter (WSA)	Turns on logging for the Web Services Adapter component.

For more information about log entry types, see OpenEdge Development: Debugging and Troubleshooting .

The following example shows how to specify one or more individual log entry types:

-logentrytypes DB.Connects,4GLTrace:2,DynObjects.UI:3

The following example shows how to specify all log entry types within a category:

-logentrytypes DynObjects.*

For more information about logging levels and log entry types, see OpenEdge Development: Debugging and Troubleshooting .

You also can turn on logging at run-time by using the LOG-ENTRY-TYPES attribute on the LOG-MANAGER system handle. For example, you can include the following line in your 4GL code:

LOG-MANAGER:LOG-ENTRY-TYPES = "DynObjects.UI"

You can turn off logging in your 4GL code by setting this attribute to the Unknown value (?). For example:

LOG-MANAGER:LOG-ENTRY-TYPES = ?

For more information about the LOG-ENTRY-TYPES attribute or the LOG-MANAGER system handle, see the OpenEdge Development: Progress 4GL Reference .